Server boostrap.ts: make forbidNonWhitelisted false#348
Open
Server boostrap.ts: make forbidNonWhitelisted false#348
Conversation
bhunt02
approved these changes
Aug 13, 2025
Collaborator
bhunt02
left a comment
There was a problem hiding this comment.
i mean it's probably fine, i thought you wanted to keep it true though for route validation?
Collaborator
Author
There's pros n cons either way. But I mostly wanted to do it this way since it will make #346 a lot easier since whoever does it probably won't need to manually test like all of those endpoints to see if our frontend was sending bad data. This can be merged when that happens |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Makes forbidNonWhitelisted false. I wanted to put this into a PR to see if this breaks any tests.
Type of change
yarn installHow Has This Been Tested?
I manually tested this with one endpoint that had validateNested with extra properties. With it true it would throw an error to the user. With this false it will now just drop the extra properties.
Checklist: